Conversation
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| { | ||
| "name": "@stll/stdnum", | ||
| "version": "0.2.0", | ||
| "version": "0.5.0", |
There was a problem hiding this comment.
🚩 Version jump from 0.2.0 to 0.5.0 skips intermediate minor versions
The version jumps from 0.2.0 directly to 0.5.0, skipping 0.3.x and 0.4.x. Looking at the git history, there are many feature PRs between the last version and this bump (#64–#72), including new generate() functionality, strict TypeScript fixes, and a build tool migration. While semver doesn't require sequential minor versions, this jump is unusual and may indicate that intermediate releases were planned but never tagged, or that a different versioning strategy is being adopted. Worth confirming this is intentional.
Was this helpful? React with 👍 or 👎 to provide feedback.
|
| Filename | Overview |
|---|---|
| package.json | Version bumped from 0.2.0 to 0.5.0; the only change in this PR. The jump of 3 minor versions is intentional to account for unreleased feature additions, but the CHANGELOG.md was not updated. |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["v0.1.0 – Initial release"] --> B["v0.2.0 – Compiled dist output added"]
B --> C["Features & fixes merged to main\n(generate, find, new validators,\nTypeScript strict, tsdown migration)"]
C --> D["This PR: package.json version → v0.5.0"]
D --> E["npm publish @stll/stdnum@0.5.0"]
style D fill:#f0f4ff,stroke:#4a6cf7
style E fill:#e6ffe6,stroke:#2e7d32
Reviews (1): Last reviewed commit: "chore: bump to v0.5.0" | Re-trigger Greptile
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| { | ||
| "name": "@stll/stdnum", | ||
| "version": "0.2.0", | ||
| "version": "0.5.0", |
There was a problem hiding this comment.
The project's CHANGELOG.md explicitly states it follows the Keep a Changelog format and adheres to Semantic Versioning, but it has not been updated to include an entry for v0.5.0 (or the earlier v0.2.0 either). The git history since v0.2.0 includes a number of meaningful changes — new validators, new capabilities like generate() and find(), TypeScript strict mode fixes, and the tsdown migration — that would be worth documenting for downstream consumers.
Consider adding a ## [0.5.0] section to CHANGELOG.md summarising the notable changes since v0.1.0 before publishing.
1 participant
Minor version bump for tsdown migration.